Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge Azure Sentinel Master into fork #28

Open
wants to merge 2,044 commits into
base: quantum
Choose a base branch
from
Open

Conversation

zhianchow
Copy link

Required items, please complete

Change(s):

  • See guidance below

Reason for Change(s):

  • See guidance below

Version Updated:

  • Required only for Detections/Analytic Rule templates
  • See guidance below

Testing Completed:

  • See guidance below

Checked that the validations are passing and have addressed any issues that are present:

  • See guidance below

Guidance <- remove section before submitting


Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:

Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR. Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process. Providing associated Issues that this resolves also easily connects the reason.

Change(s):

  • Updated syntax for XYZ.yaml

Reason for Change(s):

Version updated:

  • Yes
  • Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly. If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

  • Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

  • Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:


v-prasadboke and others added 30 commits December 11, 2024 18:49
…eDatabaseAudit-removeDC-

Repackage - Fortinet Fortiweb,OracleDatabaseAudit
GoogleThreatIntelligence: Update publisherId
dependabot bot and others added 30 commits December 26, 2024 09:09
---
updated-dependencies:
- dependency-name: aiohttp
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
…ct-platform-solution-3.0.0-change-handling-of-missing-endpoint

Change handling of missing endpoint in solution function.
Remove unused resource definitions and repackage solution
Missing Supported Values for ObjectType and TargetAppType in Audit Schema
…ectType-and-TargetAppType-in-Audit-Schema

Update ASimTester.csv
…DCRemoval

Repackage - Ivanti Unified Endpoint Management
Add Samsung Knox Asset Intelligence Sentinel Solution
…VIP-RemovedDC

Repackage - McAfee Network Security
…oPrismaCloud/Data-Connectors/aiohttp-3.10.11

Bump aiohttp from 3.9.4 to 3.10.11 in /Solutions/PaloAltoPrismaCloud/Data Connectors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.